Hupigon

Category: rat · Aliases: Hupigon, Huigezi, Grey Pigeon, Backdoor.Hupigon, Win32/Hupigon · Sample count (EMBER 2018): 146 · Enrichment: curated_sourced · Updated: 2026-10-14
Category: RatStatus: Automated SignaturePlatform: WINDOWS, X86Stage: Initial-Access, Execution, Persistence, Collection, Command-And-ControlFirst seen: 2001Actor: Chinese APT SyndicatesActor: Huang XinIndustry: defense, aerospace, government, technology, human_rightsMotivation: Cyber Espionage, Dissident Surveillance & Commercial Backdoor🕸 Explore Relationship Graph⚙ API JSON⚡ Sigma Rule💾 YARA RuleOS: Windows 11, Windows 10, Windows Server 2022
Executive Summary
Backdoor:Win32/Hupigon (universally known in China as Huigezi, translated as 'Grey Pigeon') is a classic, historically legendary Chinese Remote Access Trojan (RAT) created in 2001 by developer Huang Xin and subsequently proliferated across thousands of Chinese underground cybercrime and state-sponsored espionage operations.

Table of Contents

Overview

Backdoor:Win32/Hupigon (universally known in China as Huigezi, translated as 'Grey Pigeon') is a classic, historically legendary Chinese Remote Access Trojan (RAT) created in 2001 by developer Huang Xin and subsequently proliferated across thousands of Chinese underground cybercrime and state-sponsored espionage operations. Functioning as a comprehensive remote administration platform, Hupigon was sold openly on Chinese web portals for technical support and remote access before being banned by Chinese authorities following massive media scrutiny and commercial banking breaches in 2007. The malware features full remote desktop streaming, audio surveillance, webcam hijacking, keylogging, arbitrary process injection, and reverse connection shell commands to bypass perimeter NAT firewalls. Hupigon established the architectural blueprint for an entire generation of Chinese cyber-espionage tools (including Gh0st RAT and Poison Ivy), serving as the initial intrusion backdoor in early PLA-linked cyber espionage operations against Western defense contractors, aerospace manufacturers, and political dissidents.

Known aliases

Threat reports may refer to this family under multiple names:

Threat Actor Attribution

Attribution is probabilistic, not a science. Each link below states its confidence level and the evidence behind it.

→ Explore all Threat Actor & APT Campaign Profiles

Family Pedigree & Lineage

Malware authors regularly fork and iterate upon existing codebases. Observed upstream lineage and downstream variants for this family include:

Known Derivatives & Downstream Variants: Huigezi 2001 · Huigezi Pro Vip 2006 · Hupigon Custom Apt Builder

MITRE ATT&CK Techniques

Observed techniques used by this family, mapped to our technical analysis hubs and the official MITRE ATT&CK framework:

→ Explore the complete 226-Technique ATT&CK Threat Matrix

Tactical Mitigations

Based on the techniques used by this family, consider the following defensive strategies:

MITRE D3FEND™ Defensive Countermeasures

Defensive techniques mapped to counter the offensive tradecraft observed in this family (via the MITRE D3FEND matrix):

D3FEND IDCountermeasure NameTacticCountered ATT&CKDefensive Guidance
D3-PIADProcess Injection Analysis & DetectionDetectT1055Monitor cross-process thread creation (CreateRemoteThread) and asynchronous procedure calls (QueueUserAPC).
D3-MFAMulti-factor AuthenticationHardenT1056.001Enforce FIDO2 / WebAuthn physical tokens to render keystroke-intercepted passwords useless.
D3-PBAProcess Spawn AnalysisDetectT1059.003Inspect command-line arguments and anomalous parent-child relationships spawning from cmd.exe.
D3-WAFWeb Content Filtering & InspectionFilterT1071.001Block newly registered domains (NRDs) and inspect HTTP Host and URI headers for known C2 profiles.
D3-SDScreen Capture DetectionDetectT1113Monitor desktop graphics API calls (BitBlt, GetDC) triggered by non-standard background threads.
D3-HACHardware Device Access ControlIsolateT1125Enforce Group Policy hardware access restrictions on integrated webcams and microphones.

Exploited Vulnerabilities (CVEs)

This malware family is documented weaponizing the following common vulnerabilities and exposures:

Command & Control (C2) and Network Profile

How this family talks to its operators. C2 traffic can often identify a family even when its code and configuration are hard to analyse. Ports and patterns are historical and change between campaigns, so use them as hunting leads rather than block-only rules.

ProtocolsTCP, HTTP
Observed ports80, 8000, 2005
Identifiable from traffic aloneHigh

Indicators of Compromise

Public indicators drawn from CISA advisories and vendor reporting. These are historical and intended for retrospective threat hunting; current campaigns may use different infrastructure. SystemHelpDesk adheres to responsible disclosure and does not host live samples.

File hashes (SHA-256, sample)

Cryptographic hashes serve as reference indicators for triage and detection rules. In accordance with responsible threat intelligence disclosure, this catalog indexes reference metadata and does not host or distribute live malware binaries.

Delivery vectors

Persistence mechanisms

SIEM / EDR Ingestion: Need these reference indicators for threat hunting?

Tiered Detection Rules (Cisco CAIRN Model)

Modern threat detection requires multi-layered rule engineering. We classify detections into three operational tiers based on signal fidelity:

Tier 1 Primitive Artifact Rule (Fast Triage)

Matches raw strings and file markers. Vulnerable to binary repacking and simple obfuscation.

rule MALWARE_WIN_HUPIGON_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Hupigon"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "hupigon" ascii wide nocase
        $s2 = "hupigon" ascii wide nocase
        $s3 = "huigezi" ascii wide nocase
        $s4 = "grey pigeon" ascii wide nocase
        $s5 = "backdoor.hupigon" ascii wide nocase
        $s6 = "win32/hupigon" ascii wide nocase
    condition:
        uint16(0) == 0x5a4d and any of them
}

Tier 2 Behavioral Context Rule (Process Chains & Sigma)

Tracks parent-child process anomalies and suspicious scripting telemetry. Resilient against file renames.

title: SystemHelpDesk Detection - Hupigon (Rat) Execution & Triage
id: d043ebf7-ec81-5c1e-9e78-1a626f2ddb96
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Hupigon malware family. Detects unauthorized persistence creation via Windows
  Registry Run keys, scheduled tasks, and privilege escalation indicative of RAT installations.
references:
- https://malware-families-catalog.systemhelpdesk.com/families/hupigon
- https://malware-families-catalog.systemhelpdesk.com/defensive/backdoor-rat-protection
- https://malware-families-catalog.systemhelpdesk.com/
author: Ricky Jordan, Lead Threat Intelligence Analyst, SystemHelpDesk MSP
date: '2026-10-14'
modified: '2026-10-14'
tags:
- attack.rat
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1055
- attack.t1056_001
- attack.t1113
- attack.t1125
- attack.t1071_001
logsource:
  category: process_creation
  product: windows
detection:
  selection_process:
    Image|endswith:
    - \reg.exe
    - \schtasks.exe
    - \cmd.exe
    - \powershell.exe
    CommandLine|contains:
    - \CurrentVersion\Run
    - /create /tn
    - bypass -enc
    - net user /add
    - net localgroup administrators
  condition: selection_process
falsepositives:
- Legitimate enterprise administrative scripts during approved change windows
- Authorized IT software deployment utilities and backup management agents
level: high

Tier 3 Attribution Fingerprint Rule (High Fidelity)

Deep signature matching distinctive operational fingerprints and payload characteristics.

rule MALWARE_WIN_HUPIGON_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Hupigon tradecraft"
        tier = "T3 - Attribution Fingerprint"
        confidence = "High (Confirmed Family Signature)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        // Core family identifier & heuristic payload signatures
        $attrib_str = "hupigon" ascii wide nocase
        $pe_magic = "MZ" ascii
        $net_marker = "http" ascii nocase
    condition:
        uint16(0) == 0x5a4d and ($attrib_str and $net_marker) and filesize < 15MB
}
SOC & SIEM Rule Downloads: ⬇ Download YARA Rule (.yar) ⬇ Download Sigma Rule (YAML) ⬇ Download Sigma Rule (JSON) ⚙ Threat Profile API (JSON)

Containment & Response Steps

Home Users: If you suspect a malware infection on your personal device, disconnect from the internet immediately and run a full system scan with your antivirus software (see our TotalAV Antivirus & Security Support Guide). The steps below are intended for IT professionals responding to enterprise incidents.

Ordered checklist for responders. Adapt to your environment and engage professional support for active incidents.

  1. Terminate injected host processes and delete registered Hupigon backdoor Windows services.
  2. Block outbound TCP connections to unverified dynamic DNS endpoints on high non-standard ports.
  3. Audit systems for unauthorized webcam, microphone, or keylogger hook registrations.
  4. Apply security updates to remediate Windows legacy code execution vulnerabilities.

What to Avoid

Common mistakes during response to this family that can destroy evidence, spread the infection, or worsen recovery.

  1. Do not allow unmonitored outbound TCP connections on arbitrary high ports from client endpoints.
  2. Avoid running untrusted freeware software utilities downloaded from third-party hosting portals.
  3. Never ignore anomalous process injections into system utilities like explorer.exe.

References & External Analysis

Frequently Asked Questions

What was the Hupigon (Huigezi) trojan?

Hupigon, known as Huigezi ('Grey Pigeon'), was a prolific Chinese remote access trojan created in 2001 that laid the foundation for modern Chinese cyber-espionage backdoors.

Who developed Hupigon?

Hupigon was created by Chinese programmer Huang Xin and commercially marketed as remote management software before being outlawed due to widespread cybercrime abuse.

What capabilities does Hupigon provide?

Hupigon provides operators with remote desktop streaming, keystroke logging, webcam recording, file downloading/uploading, and reverse shell access.

What subsequent malware was influenced by Hupigon?

Hupigon's architecture and GUI design heavily influenced subsequent Chinese APT tools including Gh0st RAT, Poison Ivy, and PlugX.

What vulnerabilities were used to distribute Hupigon?

Exploit droppers delivering Hupigon leveraged early Windows vulnerabilities including CVE-2006-0003, CVE-2006-3730, and CVE-2008-2244.

How do I remove the Hupigon Rat from Windows?

Manual removal of Hupigon is highly discouraged as it may leave persistence mechanisms intact. We recommend disconnecting the device from the internet and utilizing a professional incident response service or enterprise-grade EDR software to conduct a full forensic sweep.

Is Hupigon a virus or a Rat?

Hupigon is classified as a Rat. Unlike traditional viruses that infect files, modern malware like Hupigon typically operates as a standalone payload designed to compromise systems, steal data, or deploy secondary stage implants.

What are the main symptoms of a Hupigon infection?

Symptoms of Hupigon can include unexpected system slowness, unauthorized outbound network traffic to unknown IP addresses, disabled security software, and suspicious background processes running from AppData or Temp directories.

Protect Your Network Against Rats

Want to prevent Hupigon and similar threats from compromising your organization? Read our comprehensive defensive guide: Backdoor & RAT Protection for Businesses.

📣 Threat Intel Correction or Update?

Notice an outdated IOC, unlisted alias, or disputed attribution? Threat researchers are invited to propose an update on GitHub or contact the SystemHelpDesk research desk. All community revisions are credited in our public CHANGELOG.

Need help with an active incident? Published by the SystemHelpdesk team.

Machine-readable

Get this profile as JSON: https://malware-families-catalog.systemhelpdesk.com/api/hupigon.json

Ecosystem & Interactive Environments

This profile is part of the Malware Families Catalog, a public dataset of 2,899 malware families. The catalog is also published across our ecosystem: Hugging Face, Kaggle, Zenodo, Replit, StackBlitz, CodeSandbox, and CodePen.